Access "Net" Tab in JavaScript

[Jeff Mott]

Hi all,

Let me first describe what I hope to achieve. A client site has
accumulated many files over the years, and the client wants to clear
out files that aren't used anymore. So I want to build a list of files
that *are* used.

Firebug's Net tab lists every request made for a page. I was hoping to
write some JS that would visit every page on the site and save the
requests for each page. Can I access Firebug's Net information?

Or, does anyone know of other solutions?

Thanks.

[johnjbarton]

On Oct 14, 9:49 am, Jeff Mott <jeff.mott...@gmail.com> wrote:
> Hi all,
>
> Let me first describe what I hope to achieve. A client site has
> accumulated many files over the years, and the client wants to clear
> out files that aren't used anymore. So I want to build a list of files
> that *are* used.
>
> Firebug's Net tab lists every request made for a page. I was hoping to
> write some JS that would visit every page on the site and save the
> requests for each page. Can I access Firebug's Net information?

I guess you want
http://www.softwareishard.com/blog/netexport/

[toonetown]

Another possible solution is to use the Charles Web Debugger
(www.charlesproxy.com) It's a pretty cool tool...more flexible than
the FB Net tab. (Am I allowed to say that on this group? :) )

[Rob Campbell]

no. ;)

[Honza (Jan Odvarko)]

> > (www.charlesproxy.com)  It's a pretty cool tool...more flexible than
> > the FB Net tab.  (Am I allowed to say that on this group? :) )

Could you somehow summarize what is better?
Perhaps we can improve the Net panel :-)
Honza

[Nick Fitzsimons]

2009/10/15 Honza (Jan Odvarko) <odv...@gmail.com>:

One of the key aspects of it is the fact that it's external to the
browser, so you can be absolutely certain that you're seeing things
free of anything that happens _within_ the browser.

Features I frequently use, apart from the obvious examination of
request/response cycles, headers, structure of response data (it has
nice structured viewers for XML and JSON among others):

Rewrite: automatically modify requests and/or responses, whether
headers or content, according to a specified set of rules (including
RegExp matching/replacing);
Map Remote: specify (with wildcards if desired) that requests to some
locations should be transparently changed to requests to some other
locations;
Map Local: specify (wildcards again) that requests to some locations
should be served from local files instead - extremely useful for,
amongst other things, debugging a live site that has minified JS
files: simply map them to a local copy of the debug version, insert
debug code in there, etc. without changing what's on the server;
Mirror: save all responses from a location locally;
Block cookies: useful for debugging cookie problems without having to
actually clear your cookies;
Blacklist: useful for seeing what happens to your Ajax code if the
server becomes unreachable, without having to actually take the server
down;
Throttling: see how well your site works over a dialup modem, without
dropping your broadband connection;
Breakpoints: intercept and manually edit requests and responses
according to your chosen criteria, without the browser ever realising;

... and there are various other things it can do, as well as uses for
the ones I've listed that I haven't even thought of yet :-)

Regards,

Nick.
--
Nick Fitzsimons
http://www.nickfitz.co.uk/

[John J Barton]

On Oct 15, 6:53 am, toonetown <nathan.to...@gmail.com> wrote:
...

> Another possible solution is to use the Charles Web Debugger
> (www.charlesproxy.com)  It's a pretty cool tool...more flexible than
> the FB Net tab.  (Am I allowed to say that on this group? :) )

There is also HTTPWatch, YSlow, the Google Page tool, and more.

I think Firebug should focus on those areas of net analysis that are
1) not very specialized,
2) highly related to the other panels.

jjb